fix: correct workspace type property linking API contract#45
Conversation
|
Warning Review limit reached
More reviews will be available in 59 minutes and 16 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…into fix-link-property-type
Description:
Description
The workspace work item type properties endpoint (
POST /workspaces/{slug}/work-item-types/{type_id}/properties/) expects apropertiesarray, not a singleproperty_id. The endpoint also returns HTTP 201 with no response body.Changes:
WorkspaceWorkItemTypePropertyLink:property_id: str→properties: list[str]to match API contractWorkspaceWorkItemTypeProperties.create(): removed response parsing (model_validate) since API returns empty 201Type of Change
Test Scenarios